home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group99a.txt
/
000247_icon-group-sender _Thu Dec 23 16:21:54 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id QAA00893
for icon-group-addresses; Thu, 23 Dec 1999 16:20:54 -0700 (MST)
Message-Id: <199912232320.QAA00893@baskerville.CS.Arizona.EDU>
Date: Thu, 23 Dec 1999 09:58:31 -0700 (MST)
From: Gregg Townsend <gmt>
To: icon-group
Cc: art.eschenlauer@sufsys.com, dgamey@ca.ibm.com
Subject: RE: Y2k and Icon?
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
From: Art Eschenlauer <art.eschenlauer@sufsys.com>
I saw no reply to this question. What is the Y2K readiness of Icon
implementations? I'm particularly interested in the DOS Command Line
implementation.
We have not performed a systematic evaluation of any Icon implementation
with respect to Y2K bugs, so we can't make a definitive statement.
I am not aware of any problems in the current release (9.3.2), but that
doesn't mean there aren't any, or that something won't turn up.
As with most free software, Icon is distributed as-is, without warranty,
and we cannot make any guarantees.
---------------------------------------------------------------------------
Gregg Townsend Staff Scientist The University of Arizona
gmt@cs.arizona.edu Computer Science Tucson, Arizona, USA